tests/integration/fee_estimate_query_e2e_test.py (1)

81-83: ⚠️ Potential issue | 🟠 Major | ⚡ Quick win

Strengthen assertions to validate result structure and content.

All four tests only assert result is not None, which doesn't validate the actual fee estimation response. Integration tests should verify observable network behavior beyond success/failure.

Consider asserting on the result's structure and content:

• Does result contain fee amounts (node, network, service fees)?
• Are the returned fees reasonable (positive values, within expected ranges)?
• For chunked transactions, do the fees reflect the chunk count?

💪 Example of stronger assertions

 query = FeeEstimateQuery().set_transaction(tx)
 result = query.execute(env.client)

 assert result is not None
+assert result.node_fee is not None and result.node_fee.to_tinybars() > 0
+assert result.network_fee is not None and result.network_fee.to_tinybars() > 0
+assert result.service_fee is not None and result.service_fee.to_tinybars() >= 0

(Adjust field names based on actual FeeEstimateQuery result structure)

As per coding guidelines: "Tests must assert observable network behavior, not just SUCCESS" and "Validate resulting balances, ownership, and state changes (not just transaction success)."

Also applies to: 96-98, 112-114, 130-132